home *** CD-ROM | disk | FTP | other *** search
- Path: ami-cg.GraySage.Edmonton.AB.CA!cg
- Newsgroups: comp.sys.amiga.misc
- From: cg@ami-cg.GraySage.Edmonton.AB.CA (Chris Gray)
- Subject: Re: OS features
- References: <92747544038@PAPA.NORTH.DE> <4b3h9s$1st@alterdial.UU.NET> <hmAVx*Y3f@yaps.rhein.de>
- X-NewsSoftware: GRn 2.1 Feb 19, 1994
- MIME-Version: 1.0
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- Message-ID: <cg.75pf@ami-cg.GraySage.Edmonton.AB.CA>
- Date: Thu, 11 Jan 96 00:09:12 MST
- Organization: Not an Organization
-
- In article <hmAVx*Y3f@yaps.rhein.de> arno@yaps.rhein.de (Arno Eigenwillig)
- writes:
- >
- > The one axiom relevant here is:
- >
- > All memory shall be available
- > from every context at any time
- > using a single address.
-
- etc.
-
- > If we need a very tight integration of memory, files and arbitrary
- > high- and low-level I/O streams, let's take Un*x right away and not
- > half-heartedly make AmigaOS a bad imitation.
-
- I don't totally disagree with what you are saying, but I, for one, do
- *NOT WANT UNIX*. I want something elegant, something efficient, something
- based on newer ideas of system design and goals.
-
- There are other aspects of the philosophy of AmigaOS that can be preserved
- in a memory-protected rewrite of it.
-
- I also don't think it would be terribly hard to change a lot of software
- to work within a protected environment. I for one am quite careful to
- always set mn_Length - I hope other programmers are similarly careful.
-
- Devices and handlers can all run "under the line", and retain full
- access to the real address space (or a common virtual one). Message
- copying only has to happen to/from user-mode code. Ignore MEMF_PUBLIC.
- How hard is it to do changes like that? You don't have to change the
- structure of the program, and likely not any of its philosophy.
-
- Come on, lets discuss this, folks!
-
- --
- Chris Gray cg@ami-cg.GraySage.Edmonton.AB.CA
-